Skip to content

[release-4.20] OCPBUGS-84286: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895 - #16671

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.20from
amitesh1201:CVE-2026-40895-follow-redirects-4.20
Jul 18, 2026
Merged

[release-4.20] OCPBUGS-84286: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895#16671
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.20from
amitesh1201:CVE-2026-40895-follow-redirects-4.20

Conversation

@amitesh1201

@amitesh1201 amitesh1201 commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
  • Package: follow-redirects → 1.16.0 (transitive dependency)

Changes

  • Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
  • Updated frontend/yarn.lock

Test Plan

  • yarn build succeeds (production build)

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 23, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-84286, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-84287 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
  • Package: follow-redirects → 1.16.0 (transitive dependency)
  • Risk Level: LOW (development-only dependency, not in production)

Impact

  • Production: NOT AFFECTED (webpack-dev-server and http-server are devDependencies, not deployed)
  • Development: Potentially affected (local dev server only)

Changes

  • Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
  • Added yarn resolution for follow-redirects@^1.16.0 in dynamic-demo-plugin/package.json
  • Updated frontend/yarn.lock
  • Updated dynamic-demo-plugin/yarn.lock

Test Plan

  • yarn build succeeds (production build)
  • dynamic-demo-plugin/ installs without errors

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 085a7c41-dcc8-48d5-b2cb-356210ffa26f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from cajieh and rawagner June 23, 2026 16:52
@amitesh1201

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-84286, which is invalid:

  • expected dependent Jira Issue OCPBUGS-84287 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@amitesh1201 amitesh1201 changed the title OCPBUGS-84286: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895 [release-4.20] OCPBUGS-84286: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895 Jun 24, 2026
@amitesh1201

Copy link
Copy Markdown
Contributor Author

@cajieh @jhadvig — could you take a look at this PR when you get a chance?

@germanparente

Copy link
Copy Markdown
Contributor

sustaining has the right to approve only PR's related to CVE's:

/label backport-risk-assessed
/label approved
/lgtm

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 8, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 8, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 8, 2026
@amitesh1201

Copy link
Copy Markdown
Contributor Author

/verified by CI jobs which are sufficient to verify the library bumps

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 9, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This PR has been marked as verified by CI jobs which are sufficient to verify the library bumps.

Details

In response to this:

/verified by CI jobs which are sufficient to verify the library bumps

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@amitesh1201

Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 14, 2026
Add follow-redirects resolution to pin >=1.16.0 in frontend/ workspace.

Signed-off-by: Amit Yadav <ayadav@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@amitesh1201
amitesh1201 force-pushed the CVE-2026-40895-follow-redirects-4.20 branch from 5610c9d to c1d1981 Compare July 14, 2026 09:15
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Jul 14, 2026
@openshift-ci openshift-ci Bot removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 14, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-84286, which is invalid:

  • expected dependent Jira Issue OCPBUGS-84287 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
  • Package: follow-redirects → 1.16.0 (transitive dependency)

Changes

  • Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
  • Updated frontend/yarn.lock

Test Plan

  • yarn build succeeds (production build)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@amitesh1201

Copy link
Copy Markdown
Contributor Author

/hold cancel
/jira refresh

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 14, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-84286, which is invalid:

  • expected dependent Jira Issue OCPBUGS-84287 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/hold cancel
/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@prabhapa

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 14, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amitesh1201, germanparente, prabhapa
Once this PR has been reviewed and has the lgtm label, please assign vikram-raj for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@amitesh1201

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console

@prabhapa

Copy link
Copy Markdown

/override ci/prow/e2e-gcp-console
This is infra flake. And the cypress tests that it does has no link to flowredirect lib bump

@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

@prabhapa: Overrode contexts on behalf of prabhapa: ci/prow/e2e-gcp-console

Details

In response to this:

/override ci/prow/e2e-gcp-console
This is infra flake. And the cypress tests that it does has no link to flowredirect lib bump

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

@amitesh1201: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@prabhapa

Copy link
Copy Markdown

/label approved

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2026
@amitesh1201

amitesh1201 commented Jul 17, 2026

Copy link
Copy Markdown
Contributor Author

/verified by the CI-jObs as its a simple library bump

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 17, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This PR has been marked as verified by CI jobs.

Details

In response to this:

/Verified by CI jobs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@amitesh1201

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-84286, which is invalid:

  • expected dependent Jira Issue OCPBUGS-84287 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@ocp-sustaining-admins

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-84286, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-84287 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-84287 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot
openshift-merge-bot Bot merged commit d60f0f4 into openshift:release-4.20 Jul 18, 2026
7 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@amitesh1201: Jira Issue Verification Checks: Jira Issue OCPBUGS-84286
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-84286 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Summary

  • CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
  • Package: follow-redirects → 1.16.0 (transitive dependency)

Changes

  • Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
  • Updated frontend/yarn.lock

Test Plan

  • yarn build succeeds (production build)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 4.20.0-0.nightly-2026-07-18-231008

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants